<html DIR="LTR" xmlns:MSHelp="http://msdn.microsoft.com/mshelp" xmlns:ddue="http://ddue.schemas.microsoft.com/authoring/2003/5" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tool="http://www.microsoft.com/tooltip"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=Windows-1252"></META><META NAME="save" CONTENT="history"></META><title>Submitting and Undoing Pending Changes</title><STYLE TYPE="text/css">
    body
    {
        background:    #FFFFFF;
        color: #000000;
        font-family:    Verdana;
        font-size: medium;
        font-style: normal;
        font-weight: normal;
        margin-top:    0;
        margin-bottom:    0;
        margin-left:    0;
        margin-right:    0;
        width:    100%;
    }
    
    a
    {
        color:    #0000FF;
    }
    
    a:visited
    {
        color:    #0000FF;
    }
    
    a:link
    {
        color:    #0000FF;
    }
    
    a:hover
    {
        color:    #FF0000;
        cursor: hand;
    }
    
    a:active
    {
        color:    #FF0000;
        cursor: hand;
    }
    
    div#mainSection
    {
        font-size: 70%;
        width: 100%;
    }
    
    div#mainBody
    {
        font-size: 90%;
        margin-left:    5;
        margin-top: 10;
        padding-bottom: 20;
    }
    
    div#header
    {
        background-color: #D4DFFF;
        padding-top:    0;
        padding-bottom:    0;
        padding-left:    0;
        padding-right:    0;
        width:    100%;
    }
    
    div#header table
    {
        border-bottom-color: #C8CDDE;
        border-bottom-style: solid;
        border-bottom-width: 1;
        width:    100%;
    }
    
    span#runningHeaderText
    {
        color: #003399;
        font-size: 90%;
    }
    
    span#nsrTitle
    {
        color: #003399;
        font-size: 125%;
        font-weight: 600;
    }
    
    div#header table td
    {
        color: #0000FF;
        font-size: 70%;
        margin-top:    0;
        margin-bottom:    0;
        padding-right: 20;
    }
    
    div#header table tr#headerTableRow3 td
    {
        padding-bottom: 2;
        padding-top: 5;
    }
    
    div#header table#bottomTable
    {
        border-top-color: #FFFFFF;
        border-top-style: solid;
        border-top-width: 1;
        text-align: left;
    }
    
    div#footer
    {
        font-size: 90%;
        margin-top:    0;
        margin-bottom:    0;
        margin-left:    0;
        margin-right:    0;
        padding-top:    2;
        padding-bottom:    2;
        padding-left:    2;
        padding-right:    2;
        width:    100%;
    }
    
    hr#footerHR
    {
        border-bottom-color: #EEEEFF;
        border-bottom-style: solid;
        border-bottom-width: 1;
        border-top-color: C8CDDE;
        border-top-style: solid;
        border-top-width: 1;
        height: 3;
        color: #D4DFFF;
    }
    
    div.section
    {
        padding-top:    2;
        padding-bottom:    2;
        padding-left:    16;
        padding-right:    15;
        width:    100%;
    }
    
    .heading
    {
        font-weight:    bold;
        margin-top:        18;
        margin-bottom:    8;
    }
    
    h1.heading
    {
        color: #003399;
        font-size:    125%;
    }
    
    .subHeading
    {
        font-weight:    bold;
        margin-bottom:    4;
    }
    
    h3.subHeading
    {
        color:  #003399;
        font-size: 115%;
        font-weight: bold;
    }
    
    h4.subHeading
    {
        color: #003399;
        font-size: 105%;
    }
    
    h5.subHeading
    {
        color: #003399;
        font-size: 100%;
    }
    
    img.toggle
    {
    	border: 0;
	margin-right: 5;
    }

    img.copyCodeImage
    {
	border: 0;
	margin-right: 3;
    }

    img.downloadCodeImage
    {
	border: 0;
	margin-right: 3;
    }

    img.viewCodeImage
    {
	border: 0;
	margin-right: 3;
    }

    img.note
    {
	border: 0;
	margin-right: 3;
    }

    img#languageFilterImage
    {
	border: 0;
	margin-left: 10;
	vertical-align: middle;
    }

    img#membersOptionsFilterImage
    {
	border: 0;
	margin-left: 10;
	vertical-align: middle;
    }

    img#toggleAllImage
    {
	margin-left: 4;
	vertical-align: middle;
    }
    
    div#mainSection table
    {
        border: 0;
        font-size: 100%;
        width:    100%;
    }
    
    div#mainSection table th
    {
        background:    #EFEFF7;
        border-bottom-color: #C8CDDE;
        border-bottom-style: solid;
        border-bottom-width: 1;
        color: #000066;
        padding-left: 5;
        padding-right: 5;
    }
    
    div#mainSection table td
    {
        background:    #F7F7FF;
        border-top-color: #FFFFFF;
        border-top-style: solid;
        border-top-width: 1;
        padding-left: 5;
        padding-right: 5;
    }
    
    div#mainSection table td.imageCell
    {
        white-space: nowrap;
    }
    
    div.code table
    {
        border: 0;
        font-size: 95%;
        margin-bottom: 5;
        width: 100%
    }
    
    div.code table th
    {    
        background:    #EFEFF7;
        border-bottom-color: #C8CDDE;
        border-bottom-style: solid;
        border-bottom-width: 1;
        color: #000066;
        font-weight: bold;
        padding-left: 5;
        padding-right: 5;
    }
    
    div.code table td
    {
        background:    #F7F7FF;
        border-top-color: #FFFFFF;
        border-top-style: solid;
        border-top-width: 1;
        padding-left: 5;
        padding-right: 5;
        padding-top: 5;
    }
    
    div.alert table
    {
        border: 0;
        font-size: 100%;
        width:    100%;
    }
    
    div.alert table th
    {
        background:    #EFEFF7;
        border-bottom-width: 0;
        color: #000066;
        padding-left: 5;
        padding-right: 5;
    }
    
    div.alert table td
    {
        background:    #F7F7FF;
        border-top-color: #FFFFFF;
        border-top-style: solid;
        border-top-width: 1;
        padding-left: 5;
        padding-right: 5;
    }
    
    .copyCode
    {
        color: #0000ff;
        font-size: 90%;
        font-weight: normal;
    }
    
    .downloadCode
    {
        color: #0000ff;
        font-size: 90%;
        font-weight: normal;
    }
    
    .viewCode
    {
        color: #0000ff;
        font-size: 90%;
        font-weight: normal;
    }
    
    div.code pre
    {
        font-family:    Monospace, Courier New, Courier;
        font-size: 105%;
        color:    #000066;
        word-wrap:    break-word;
    }
    
    code
    {
        font-family:    Monospace, Courier New, Courier;
        font-size: 105%;
        color:    #000066;
    }
    
    dl
    {
        margin-top:    0;
        padding-left:    1;
    }
    
    dt
    {
        font-style:    italic;
    }
    
    dd
    {
        margin-bottom:    0;
        margin-left:    0;
    }
    
    ul
    {
        margin-left: 17;
        list-style-type: disc;
    }
    
    ul ul
    {
        margin-bottom: 4;
        margin-left: 17;
        margin-top: 3;
        list-style-type: disc;
    }
    
    ol
    {
        margin-left: 24;
        list-style-type: decimal;
    }
    
    ol ol
    {
        margin-bottom: 4;
        margin-left: 24;
        margin-top: 3;
        list-style-type: lower-alpha;
    }
    
    li
    {
        margin-bottom: 3;
    }
    
    p
    {
        margin-top: 0;
        margin-bottom: 15;
    }
    
    .tip
    {
        color:    #0000FF;
        font-style: italic;
        cursor:hand;
        text-decoration:underline;
    }
    
    .languageFilter
    {
        color:    #0000FF;
        cursor:hand;
        text-decoration:underline;
        padding-bottom:4;
    }
    
    .math
    {
        font-family: Times New Roman;
        font-size: 125%
    }
    
    .sourceCodeList
    {
        font-family: Verdana;
        font-size: 90%;    
    }
    
    pre.viewCode
    {
        width: 100%;
        overflow: auto;
    }
    
    MSHelp\:link
    {
        text-decoration: underline;
        color: #0000ff; 
        hoverColor: #3366ff;
        filterString: ;
    }
</STYLE>
</head>
<body><input type="hidden" id="userDataCache" class="userDataStyle"></input><input type="hidden" id="hiddenScrollOffset"></input><img id="dropDownImage" style="display:none; height:0; width:0;" src="drpdown.gif"><img id="dropDownHoverImage" style="display:none; height:0; width:0;" src="drpdown_orange.gif"><img id="collapseImage" style="display:none; height:0; width:0;" src="collapse.gif"><img id="expandImage" style="display:none; height:0; width:0;" src="exp.gif"><img id="copyImage" style="display:none; height:0; width:0;" src="copycode.gif"><img id="copyHoverImage" style="display:none; height:0; width:0;" src="copycodeHighlight.gif"><div id="header"><table width="100%" id="topTable"><tr id="headerTableRow1"><td align="left"><span id="runningHeaderText"></span></td></tr><tr id="headerTableRow2"><td align="left"><span id="nsrTitle">Submitting and Undoing Pending Changes</span></td></tr><tr id="headerTableRow3"></tr></table></div><div id="mainSection"><div id="mainBody"><div id="allHistory" class="saveHistory"></div>
				<p>You can check in changes to Team Foundation version control
 files into the version control server by using the <b>Pending Changes</b> window or the <b>Check In</b> dialog box. Changes are checked in as a group and tracked on the server as a changeset. During a check-in, you can add explanatory comments, associate work items with the changeset, and review adherence to check-in policy. Various aspects of the check-in process can be customized by your server administrator.</p>
			<h1 class="heading">How the check-in process works</h1><div id="sectionSection0" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
					<p xmlns="">When you initiate a check-in operation, the source file updates either succeed as a group or fail as a group. If any of the changes in the list of pending changes cannot be submitted to the server (for example, because of a conflict), none of the changes are committed and a changeset is not created.</p>
					<p xmlns="">During a check-in operation:</p>
					<ul xmlns=""><li class="unordered">
							Compliance with check-in policy is validated.<br /><br />
						</li><li class="unordered">
							The changes are committed to the server as a changeset.<br /><br />
						</li><li class="unordered">
							Files that were checked out are returned to a read-only state. Your changes appear in the server and can be retrieved by other users.<br /><br />
						</li><li class="unordered">
							E-mail is delivered to team members who have subscribed for check-in notification.<br /><br />
							<div class="alert"><table width="100%" cellspacing="0" cellpadding="0"><tr><th align="left">Note </th></tr><tr><td>
								In Team Explorer Everywhere 2010
, you cannot subscribe for check-in notification. If you use another client of Team Foundation Server
 to configure the subscriptions, you can receive emails when check-ins occur.<p></p>
							</td></tr></table><p></p></div>
						</li><li class="unordered">
							Work items are updated.<br /><br />
						</li></ul>
				</content></div><h1 class="heading">Customizing the check-in process</h1><div id="sectionSection1" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
					<p xmlns="">An administrator for Team Foundation
 can configure the check-in notes and check-in policies that apply to a given team project. For more information, see <a href="setqualitygates.htm" target="_blank">Setting and Enforcing Quality Gates</a>.</p>
				</content></div><h1 class="heading">Common Tasks</h1><div id="sectionSection2" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
					<h3 class="subHeading" xmlns=""></h3><table xmlns=""><tr>
								<th>
									Task
								</th>
								<th>
									Supporting Content
								</th>
							</tr><tr>
							<td>
								<p>
									<b>View and manage pending changes:</b> Understand the types of locally-persisted changes and how you can manage them. Identify all the pending check-in changes in one or more workspaces. You can also view the work items that are associated with the pending changes.</p>
							</td>
							<td>
								<ul><li class="unordered">
										
											<a href="viewyourpendingchanges.htm" target="_blank">View and Manage All Pending Changes in Your Workspace</a>
										<br /><br />
									</li><li class="unordered">
										
											<a href="#TypesOfPendingChanges">Types of Pending Changes</a>
										<br /><br />
									</li><li class="unordered">
										
											<a href="viewotherpendingchanges.htm" target="_blank">View Pending Changes in Other Workspaces</a>
										<br /><br />
									</li><li class="unordered">
										
											<a href="detailspendingchanges.htm" target="_blank">View Work Item Details from Pending Changes Window</a>
										<br /><br />
									</li></ul>
							</td>
						</tr><tr>
							<td>
								<p>
									<b>Check in pending changes:</b> After you have reviewed your pending changes, you can check in those changes. As part of the check-in process, you can associate check-in notes or work items with the changeset. If your changes do not meet the check-in policies that are defined for the team project, you can override the check-in policy. You should override a check-in policy only after careful consideration. Check-in policies exist to protect the quality, stability, and performance of your application.</p>
								<div class="alert"><table width="100%" cellspacing="0" cellpadding="0"><tr><th align="left">Important </th></tr><tr><td>
									
										Team Explorer Everywhere 2010
 does not support gated check-ins. If you attempt to check in pending changes to an area of your application that is protected by gated check-ins, an error or warning appears. Depending on your server configuration, your build might still start.<p></p>
								</td></tr></table><p></p></div>
							</td>
							<td>
								<ul><li class="unordered">
										
											<a href="checkinpending.htm" target="_blank">Check in Pending Changes</a>
										<br /><br />
									</li><li class="unordered">
										
											<a href="assocwitemchangeset.htm" target="_blank">Associate Work Items with Changesets</a>
										<br /><br />
									</li><li class="unordered">
										
											<a href="overridecheckinpolicy.htm" target="_blank">Override a Check-In Policy</a>
										<br /><br />
									</li></ul>
							</td>
						</tr><tr>
							<td>
								<p>
									<b>Resolve unwanted or incorrect changes:</b> You might determine that one or more pending changes are not needed. You can undo those pending changes. </p>
								<div class="alert"><table width="100%" cellspacing="0" cellpadding="0"><tr><th align="left">Important </th></tr><tr><td>
									If you have already checked in changes that are unwanted or incorrect, you cannot roll back those changes by using Team Explorer Everywhere 2010
. You must use the command-line client for Visual Studio
 to perform a <b>rollback</b> operation.<p></p>
								</td></tr></table><p></p></div>
							</td>
							<td>
								<ul><li class="unordered">
										
											<a href="undopending.htm" target="_blank">Undo Pending Changes</a>
										<br /><br />
									</li><li class="unordered">
										
											<a href="http://go.microsoft.com/fwlink/?LinkID=184700" target="_blank" alt=""><linkText xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">Rollback Command (Team Foundation Version Control)</linkText></a> on the Microsoft Web site<br /><br />
									</li></ul>
							</td>
						</tr></table>
				</content></div><a name="TypesOfPendingChanges"></a><a name="submitchanges#TypesOfPendingChanges"></a><h1 class="heading">Types of Pending Changes</h1><div id="sectionSection3" class="section"><content xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">
					<p xmlns="">The following table explains the types of pending changes that you can check in.</p>
					<h3 class="subHeading" xmlns=""></h3><table xmlns=""><tr>
								<th>
									Pending Change
								</th>
								<th>
									Description
								</th>
							</tr><tr>
							<td>
								<p>Add</p>
							</td>
							<td>
								<p>Files that you add to Team Foundation version control
 are treated as pending <b>add</b> changes.</p>
							</td>
						</tr><tr>
							<td>
								<p>Edit</p>
							</td>
							<td>
								<p>When you check out a file to modify in your workspace, Team Foundation
 makes it writable and adds an <b>edit</b> change to the list of pending changes for the workspace.</p>
							</td>
						</tr><tr>
							<td>
								<p>Merge</p>
							</td>
							<td>
								<p>When you merge changes made in different branches, a <b>merge</b> change is added to the list of pending changes for the workspace.</p>
							</td>
						</tr><tr>
							<td>
								<p>Rollback</p>
							</td>
							<td>
								<p>The command-line client for Visual Studio
 can be used to run the <b>tf rollback</b> command to eliminate the effect of one or more changesets on an item. </p>
								<div class="alert"><table width="100%" cellspacing="0" cellpadding="0"><tr><th align="left">Note </th></tr><tr><td>
									You cannot use the <b>rollback</b> command from the Cross-platform Command-line Client for Team Foundation Server.<p></p>
								</td></tr></table><p></p></div>
								<p>When the  command is run, <b>rollback</b> is added to the pending changes. For more information, see the following topic on the Microsoft Web site: <a href="http://go.microsoft.com/fwlink/?LinkID=184700" target="_blank" alt=""><linkText xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">Rollback Command (Team Foundation Version Control)</linkText></a>.</p>
							</td>
						</tr><tr>
							<td>
								<p>Delete</p>
							</td>
							<td>
								<p>When you delete a file in Team Foundation version control
, it stays on the server until the <b>delete</b> is checked in. For more information, see <a href="movedeletevcfiles.htm" target="_blank">Move, Rename, and Delete Version-Controlled Files and Folders</a>.</p>
							</td>
						</tr><tr>
							<td>
								<p>Undelete</p>
							</td>
							<td>
								<p>When you undelete a file, after you check in the <b>undelete</b> change, the file is restored from the server during the check-in process. For more information, see the following topic on the Microsoft Web site: <a href="http://go.microsoft.com/fwlink/?LinkID=183581" target="_blank" alt=""><linkText xmlns="http://ddue.schemas.microsoft.com/authoring/2003/5">Undelete Command (Team Foundation Version Control)</linkText></a>.</p>
							</td>
						</tr><tr>
							<td>
								<p>Rename (includes file moves)</p>
							</td>
							<td>
								<p>When you rename or move a file, it is renamed or moved on the local disk, but the changes are not reflected on the server until you check in the <b>rename</b> change. For more information, see <a href="movedeletevcfiles.htm" target="_blank">Move, Rename, and Delete Version-Controlled Files and Folders</a>.</p>
							</td>
						</tr><tr>
							<td>
								<p>Branch</p>
							</td>
							<td>
								<p>When you branch a branch, the change takes place immediately on the server; no pending change is generated. However, when you branch a folder, the branch operation is not committed until the <b>branch</b> change is checked in.</p>
								<div class="alert"><table width="100%" cellspacing="0" cellpadding="0"><tr><th align="left">Important </th></tr><tr><td>
									If, during a branch operation, you convert the source and target folders to branches, that change is committed directly and does not need to be checked in. If a folder is converted to a branch, you cannot use Team Explorer Everywhere to convert it back to a folder.<p></p>
								</td></tr></table><p></p></div>
							</td>
						</tr><tr>
							<td>
								<p>Type</p>
							</td>
							<td>
								<p>When you change the file encoding of a file, the operation is not committed until the <b>type</b> change is checked in.</p>
							</td>
						</tr></table>
				</content></div><h1 class="heading"><span id="seeAlsoNoToggle">See Also</span></h1><div id="seeAlsoSection" class="section"><h4 class="subHeading">Concepts</h4><a href="workspaces.htm" target="_blank">Working with Team Foundation Server Workspaces</a><br /><a href="getlocalcopy.htm" target="_blank">Getting a Local Copy of Files from the Version Control Server</a><br /><a href="usingversionctrl.htm" target="_blank">Using Version Control</a><br /><br /></div><!--[if gte IE 5]>
			<tool:tip element="seeAlsoToolTip" avoidmouse="false"/><tool:tip element="languageFilterToolTip" avoidmouse="false"/>
		<![endif]--></div><div id="footer"><hr /><p /></div></div></body></html>